Method and system for operating a configuration platform

ABSTRACT

A system for operating a configuration platform. The system comprising a conversion pipeline, the conversion pipeline allowing converting a first set of data associated with a computer-aided design (CAD) system into polygon meshes suitable for rendering of the portion of a monument and configuration data. The system also comprising a content management system, the content management system storing the polygon meshes and the configuration data; and a 3D real-time engine, the 3D real-time engine allowing to determine, based on the configuration data, at least one of the positioning of the monument, the material surface associated with the monument, the material grain direction associated with the monument, the lighting associated with the monument, the annotations associated with the monument, the alternate states associated with the monument and the kinematic sequence associated with the monument; and to render the portion of the monument by the 3D real-time engine.

FIELD

The present application claims priority to U.S. Provisional PatentApplication No. 62/611,643, filed Dec. 29, 2017, the entirety of whichis incorporated herein by reference.

The present technology relates to systems and methods for operating aconfiguration platform. In particular, the systems and methods aim atallowing real-time configuration and real-time visualisation of 3Dmodels, such as, but not limited to, 3D models representing aircraftcabin interiors.

BACKGROUND

High end business aircraft, such as the Challenger™ and the Global™business aircraft from Bombardier Inc., require a high level ofcustomisation to meet customer requirements that typically make eachcabin interior unique from one aircraft to another. In addition tohandling such high level of customisation, aircraft OEMs also need toensure that standards and regulations (such as, but not limited to,regulations from the Federal Aviation Administration, Transport Canadaand the European Aviation Safety Agency) are also met. This result in ahighly complex process to be conducted before a final cabin interiorconfiguration can be set and be ready for engineering and manufacturing.Such process typically comprises customer needs analysis, cabin interiorconfiguration and optimization, cabin interior configuration renderingand multiple iterations between the aircraft OEM teams and the customer.

Cabin interior configuration modeling systems currently availablerequire a manually intensive process that has very limited abilities toproduce real-time rendering. As a result, aircraft OEM personnel has tomanually capture customer requirements, for example through one or morein-person meetings with the customer (or personnel acting on behalf ofthe customer), to then be able to generate aircraft cabin interiorprototypes, for example by using 3D CAD/CAM (computer aideddesign/computer aided manufacturing) tools.

Current approaches provide limited real-time interactions between thecustomer and an aircraft cabin interior prototype as 3D modeling mayrequire days of work, a dedicated team and dedicated systems to properlyoperate the 3D CAD/CAM tool used to create a representation of theaircraft cabin interior prototype. This limitation may be even moreprevalent in the context of configuring a business aircraft cabininterior, as in-person meetings between the aircraft OEM personnel andthe customer may occur outside of the premises of the aircraft OEM.

In addition, aircraft cabin interior typically comprise a vast number ofcommodities, monuments and accessories for which correspondingengineering data is typically stored and managed by aircraft OEMs and/orsuppliers of the aircraft OEMs. The engineering data may comprise allthe required information to generate 3D model but typically comprise toomuch information and details to be efficiently use for the purpose ofaircraft interior configuration. In many instances, the engineering dataneeds to be manually trimmed so that only information relevant to therendering of the aircraft cabin interior are used in the context ofconfiguring the aircraft cabin interior. This process may be cumbersome,difficult to manage and/or prone to errors and/or inconsistencies.

Due to the high level of customization of each one of the commodities,monuments and accessories and the complexity of the associatedengineering data, determining appropriate configurations that meetcertain constraints (e.g., customer requirements, regulationsrequirements, etc.) require a thorough understanding of both availablecustomizations and constraints by the individual in charge of generatinga given aircraft interior configuration. This approach may lead tosubstantial turnaround time between a configuration request for a givencustomization is made and the deliverables created of the resultinggiven customization (which may comprise the rendering of the givencustomization).

Even when the given customization is properly rendered, modificationsincluding, for example, propagating a given customization associatedwith a given monument to other monuments sharing a same monumentcategory may need to be done manually. As an example, but without beinglimitative, such situation may occur when there is a need forpropagating a given customization of a surface material associated withan armrest of a passenger seat to surface materials associated witharmrests of other passenger seats.

Improvements may be therefore desirable.

The subject matter discussed in the background section should not beassumed to be prior art merely as a result of its mention in thebackground section. Similarly, a problem mentioned in the backgroundsection or associated with the subject matter of the background sectionshould not be assumed to have been previously recognized in the priorart. The subject matter in the background section merely representsdifferent approaches.

SUMMARY

Embodiments of the present technology have been developed based ondevelopers' appreciation of at least one shortcoming associated with theprior art.

In particular, such shortcomings may comprise (1) a limited ability togenerate real-time rendering of aircraft cabin interiors; (2) a limitedability to provide a configuration platform that can be accessed,controlled and easily used remotely by aircraft OEMs personnel; (3) alimited ability to easily leverage engineering data for the purpose ofreal-time rendering and real-time configuration; (4) a limited abilityto easily apply configurations rules and/or (5) a limited ability toeasily propagate a given customization associated with a given monumentto other monuments sharing a same monument category.

In one aspect, various implementations of the present technology providea system for operating a configuration platform, the system comprising:

a conversion pipeline, the conversion pipeline allowing converting afirst set of data associated with a computer-aided design (CAD) systeminto polygon meshes suitable for rendering of the portion of a monumentand configuration data, the configuration data comprising at least oneof a positioning of the monument, a material surface associated with themonument, a material grain direction associated with the monument,lighting associated with the monument, annotations associated with themonument, alternate states associated with the monument and a kinematicsequence associated with the monument;

a content management system, the content management system storing thepolygon meshes and the configuration data; and

a 3D real-time engine, the 3D real-time engine allowing to determine,based on the configuration data, at least one of the positioning of themonument, the material surface associated with the monument, thematerial grain direction associated with the monument, the lightingassociated with the monument, the annotations associated with themonument, the alternate states associated with the monument and thekinematic sequence associated with the monument; and to render theportion of the monument by the 3D real-time engine.

In other aspects, various implementations of the present technologyprovide a method of converting a first set of data associated with acomputer-aided design (CAD) system polygon meshes and configurationdata, the method comprising:

accessing the first set of data, the first set of data defining a datacollector associated with a monument of an aircraft cabin interior, thedata collector comprising a body defining a 3D object representative ofat least a portion of the monument and metadata defining informationassociated with the 3D object;

converting the body into polygon meshes suitable for rendering by a 3Dreal-time engine of a configuration platform;

generating, based on an analysis of the metadata, configuration data,the configuration data comprising at least one of a positioning of themonument, a material surface associated with the monument, a materialgrain direction associated with the monument, lighting associated withthe monument, annotations associated with the monument, alternate statesassociated with the monument and a kinematic sequence associated withthe monument; and

compiling the polygon meshes and the configuration data in a data formatsuitable for representation and behaviours by the 3D real-time engine.

In other aspects, various implementations of the present technologyprovide a method of operating a configuration platform, the methodcomprising:

accessing, from a content management system, monument datarepresentative of at least a portion of a monument of an aircraft cabininterior, the monument data comprising polygon meshes suitable forrendering of the portion of the monument by a 3D real-time engine andconfiguration data, the configuration data comprising at least one of apositioning of the monument, a material surface associated with themonument, a material grain direction associated with the monument,lighting associated with the monument, annotations associated with themonument, alternate states associated with the monument and a kinematicsequence associated with the monument;

determining, based on the configuration data, at least one of thepositioning of the monument, the material surface associated with themonument, the material grain direction associated with the monument, thelighting associated with the monument, the annotations associated withthe monument, the alternate states associated with the monument and thekinematic sequence associated with the monument; and

rendering the portion of the monument by the 3D real-time engine.

In other aspects, various implementations of the present technologyprovide a method of updating a content management system associated witha configuration platform, the method comprising:

accessing the content management system, the content management systemcomprising monument data representative of a monument of an aircraftcabin interior, the monument data comprising polygon meshes suitable forrendering of at least a portion of the monument by a 3D real-time engineand configuration data, the configuration data comprising at least oneof a positioning of the monument, a material surface associated with themonument, a material grain direction associated with the monument,lighting associated with the monument, annotations associated with themonument, alternate states associated with the monument and a kinematicsequence associated with the monument;

accessing parameters defining a property of a material, the parametersbeing reflective of at least one of a finish type associated with thematerial, a scale associated with the material, a position associatedwith the material and a position associated with the material;

defining applicability of the parameters to the monument; and

assigning, based on the defined applicability of the parameters to themonument, a component identifier to the monument data and to othermonuments data based on a relationship between the monument data and theother monuments data.

In other aspects, various implementations of the present technologyprovide a method of applying configuration rules, the configurationrules relating to an operation of a configuration platform, the methodcomprising:

accessing, from a content management system, monument datarepresentative of a monument of an aircraft cabin interior, the monumentdata comprising polygon meshes suitable for rendering of a portion ofthe monument by a 3D real-time engine and configuration data, theconfiguration data comprising at least one of a positioning of themonument, a material surface associated with the monument, a materialgrain direction associated with the monument, lighting associated withthe monument, annotations associated with the monument, alternate statesassociated with the monument and a kinematic sequence associated withthe monument;

accessing configuration rules data, the configuration rules datamodeling internal monument configuration rules and external monumentconfiguration rules, the internal monument configuration rules relatingto an internal configuration of the monument affecting the monumentitself and the external monument configuration rules relating to anexternal configuration of the monument affecting an environment in whichthe monument is to be represented;

applying at least a subset of the configuration rules data to themonument data; and

rendering the monument by the 3D real-time engine, the rendering beingbased on the internal configuration rules and the external configurationrules to represent the portion of the monument.

In other aspects, various implementations of the present technologyprovide a method of propagating a configuration setting of a 3D model toother 3D models, the 3D model and the other 3Ds being part of a same 3Dmodel category, the method comprising:

-   -   dividing the 3D model into a first plurality of surfaces, the        first plurality of surfaces being 3D model surfaces visible upon        being rendered by a 3D engine;    -   associating to each one of the first plurality of surfaces, a        unique surface identifier;    -   for each one of the other 3D models:        -   dividing the one of the other 3D models into a second            plurality of surfaces;        -   establishing a correspondence between at least some of the            second plurality of surfaces and at least some of the first            plurality of surfaces, based on a correspondence between the            3D model and the one of the other 3D models;        -   associating, for each one of the second plurality of            surfaces corresponding to one of the first plurality of            surfaces, the unique surface identifier associated with the            corresponding one of the first plurality of surfaces;    -   selecting the configuration setting of the 3D model;    -   determining the unique identifier of the 3D model to which the        configuration setting is to be applied; and    -   propagating, based on the unique identifier of the 3D model, the        configuration setting to the other 3D models to which the        configuration setting is to be applied.

In other aspects, various implementations of the present technologyprovide a computer-based system, such as, for example, but without beinglimitative, an electronic device comprising at least one processor and amemory storing program instructions for operating a configurationplatform, the program instructions being executable by one or moreprocessors of the computer-based system to carry out one or more of theabove-recited methods.

In other aspects, various implementations of the present technologyprovide a non-transitory computer-readable medium storing programinstructions for operating a configuration platform, the programinstructions being executable by a processor of a computer-based systemto carry out one or more of the above-recited methods.

In the context of the present specification, unless expressly providedotherwise, an “electronic device”, an “electronic device”, a “server”,a, “remote server”, and a “computer-based system” are any hardwareand/or software appropriate to the relevant task at hand. Thus, somenon-limiting examples of hardware and/or software include computers(servers, desktops, laptops, netbooks, etc.), smartphones, tablets,network equipment (routers, switches, gateways, etc.) and/or combinationthereof.

In the context of the present specification, unless expressly providedotherwise, the expression “computer-readable medium” and “memory” areintended to include media of any nature and kind whatsoever,non-limiting examples of which include RAM, ROM, disks (CD-ROMs, DVDs,floppy disks, hard disk drives, etc.), USB keys, flash memory cards,solid state-drives, and tape drives.

In the context of the present specification, a “database” is anystructured collection of data, irrespective of its particular structure,the database management software, or the computer hardware on which thedata is stored, implemented or otherwise rendered available for use. Adatabase may reside on the same hardware as the process that stores ormakes use of the information stored in the database or it may reside onseparate hardware, such as a dedicated server or plurality of servers.

In the context of the present specification, unless expressly providedotherwise, an “indication” of an information element may be theinformation element itself or a pointer, reference, link, or otherindirect mechanism enabling the recipient of the indication to locate anetwork, memory, database, or other computer-readable medium locationfrom which the information element may be retrieved. For example, anindication of a file could include the file itself (i.e. its contents),or it could be a unique file descriptor identifying the file withrespect to a particular file system, or some other means of directingthe recipient of the indication to a network location, memory address,database table, or other location where the file may be accessed. As oneskilled in the art would recognize, the degree of precision required insuch an indication depends on the extent of any prior understandingabout the interpretation to be given to information being exchanged asbetween the sender and the recipient of the indication. For example, ifit is understood prior to a communication between a sender and arecipient that an indication of an information element will take theform of a database key for an entry in a particular table of apredetermined database containing the information element, then thesending of the database key is all that is required to effectivelyconvey the information element to the recipient, even though theinformation element itself was not transmitted as between the sender andthe recipient of the indication.

In the context of the present specification, unless expressly providedotherwise, the words “first”, “second”, “third”, etc. have been used asadjectives only for the purpose of allowing for distinction between thenouns that they modify from one another, and not for the purpose ofdescribing any particular relationship between those nouns. Thus, forexample, it should be understood that, the use of the terms “firstserver” and “third server” is not intended to imply any particularorder, type, chronology, hierarchy or ranking (for example) of/betweenthe server, nor is their use (by itself) intended imply that any “secondserver” must necessarily exist in any given situation. Yet as anotherexample, it should be understood that, the use of the terms “firstdirection” and “third direction” is not intended to imply, unlessspecified otherwise, any particular order, type, chronology, hierarchyor ranking (for example) of/between the directions, nor is their use (byitself) intended imply that any “second direction” must necessarilyexist in any given situation. Further, as is discussed herein in othercontexts, reference to a “first” element and a “second” element does notpreclude the two elements from being the same actual real-world element.Thus, for example, in some instances, a “first” server and a “second”server may be the same software and/or hardware, in other cases they maybe different software and/or hardware.

Implementations of the present technology each have at least one of theabove-mentioned object and/or aspects, but do not necessarily have allof them. It should be understood that some aspects of the presenttechnology that have resulted from attempting to attain theabove-mentioned object may not satisfy this object and/or may satisfyother objects not specifically recited herein.

Additional and/or alternative features, aspects and advantages ofimplementations of the present technology will become apparent from thefollowing description, the accompanying drawings and the appendedclaims.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the present technology, as well as otheraspects and further features thereof, reference is made to the followingdescription which is to be used in conjunction with the accompanyingdrawings, where:

FIG. 1 is a diagram of a computer system suitable for implementing thepresent technology and/or being used in conjunction with implementationsof the present technology;

FIG. 2 is a diagram of a networked computing environment in accordancewith an embodiment of the present technology;

FIG. 3 is a perspective view of an aircraft cabin interior in accordancewith an embodiment of the present technology;

FIGS. 4 to 7 are screenshots illustrating embodiments of graphical userinterfaces in accordance with embodiments of the present technology;

FIG. 8 illustrates a 3D rendering of an aircraft cabin interior inaccordance with an embodiment of the present technology;

FIGS. 9 and 10 illustrate diagrams of various additional softwaremodules in accordance with embodiments of the present technology;

FIGS. 11 and 12 illustrate screenshots showing material propertiesassociated with a monument in accordance with embodiments of the presenttechnology;

FIG. 13 illustrates variations of lighting modeling in accordance withembodiments of the present technology;

FIGS. 14 and 15 illustrate examples of multiple levels of configurationand collectors in accordance with embodiments of the present technology;

FIG. 16 illustrates rule formats and a rule example in accordance withembodiments of the present technology;

FIGS. 17 and 18 illustrate embodiments of a method of propagating aconfiguration setting of a 3D model in accordance with embodiments ofthe present technology;

FIG. 19 is a flowchart illustrating a first computer-implemented methodimplementing embodiments of the present technology;

FIG. 20 is a flowchart illustrating a second computer-implemented methodimplementing embodiments of the present technology;

FIG. 21 is a flowchart illustrating a third computer-implemented methodimplementing embodiments of the present technology;

FIG. 22 is a flowchart illustrating a fourth computer-implemented methodimplementing embodiments of the present technology; and

FIG. 23 is a flowchart illustrating a fifth computer-implemented methodimplementing embodiments of the present technology.

It should also be noted that, unless otherwise explicitly specifiedherein, the drawings are not to scale.

DETAILED DESCRIPTION

The examples and conditional language recited herein are principallyintended to aid the reader in understanding the principles of thepresent technology and not to limit its scope to such specificallyrecited examples and conditions. It will be appreciated that thoseskilled in the art may devise various arrangements which, although notexplicitly described or shown herein, nonetheless embody the principlesof the present technology and are included within its spirit and scope.

Furthermore, as an aid to understanding, the following description maydescribe relatively simplified implementations of the presenttechnology. As persons skilled in the art would understand, variousimplementations of the present technology may be of a greatercomplexity.

In some cases, what are believed to be helpful examples of modificationsto the present technology may also be set forth. This is done merely asan aid to understanding, and, again, not to define the scope or setforth the bounds of the present technology. These modifications are notan exhaustive list, and a person skilled in the art may make othermodifications while nonetheless remaining within the scope of thepresent technology. Further, where no examples of modifications havebeen set forth, it should not be interpreted that no modifications arepossible and/or that what is described is the sole manner ofimplementing that element of the present technology.

Moreover, all statements herein reciting principles, aspects, andimplementations of the present technology, as well as specific examplesthereof, are intended to encompass both structural and functionalequivalents thereof, whether they are currently known or developed inthe future. Thus, for example, it will be appreciated by those skilledin the art that any block diagrams herein represent conceptual views ofillustrative circuitry embodying the principles of the presenttechnology. Similarly, it will be appreciated that any flowcharts, flowdiagrams, state transition diagrams, pseudo-code, and the like representvarious processes which may be substantially represented incomputer-readable media and so executed by a computer or processor,whether or not such computer or processor is explicitly shown.

The functions of the various elements shown in the figures, includingany functional block labeled as a “processor” or a “graphics processingunit”, may be provided through the use of dedicated hardware as well ashardware capable of executing software in association with appropriatesoftware. When provided by a processor, the functions may be provided bya single dedicated processor, by a single shared processor, or by aplurality of individual processors, some of which may be shared. In someembodiments of the present technology, the processor may be a generalpurpose processor, such as a central processing unit (CPU) or aprocessor dedicated to a specific purpose, such as a graphics processingunit (GPU). Moreover, explicit use of the term “processor” or“controller” should not be construed to refer exclusively to hardwarecapable of executing software, and may implicitly include, withoutlimitation, digital signal processor (DSP) hardware, network processor,application specific integrated circuit (ASIC), field programmable gatearray (FPGA), read-only memory (ROM) for storing software, random accessmemory (RAM), and non-volatile storage. Other hardware, conventionaland/or custom, may also be included.

Software modules, or simply modules which are implied to be software,may be represented herein as any combination of flowchart elements orother elements indicating performance of process steps and/or textualdescription. Such modules may be executed by hardware that is expresslyor implicitly shown.

With these fundamentals in place, we will now consider some non-limitingexamples to illustrate various implementations of aspects of the presenttechnology.

Referring to FIG. 1, there is shown a computer system 100 suitable foruse with some implementations of the present technology, the computersystem 100 comprising various hardware components including one or moresingle or multi-core processors collectively represented by processor110, a graphics processing unit (GPU) 111, a solid-state drive 120, arandom access memory 130, a display interface 140, and an input/outputinterface 150.

Communication between the various components of the computer system 100may be enabled by one or more internal and/or external buses 160 (e.g. aPCI bus, universal serial bus, IEEE 1394 “Firewire” bus, SCSI bus,Serial-ATA bus, etc.), to which the various hardware components areelectronically coupled. The display interface 140 may be coupled to amonitor 142 (e.g. via an HDMI cable 144) visible to a user 170, and theinput/output interface 150 may be coupled to a touchscreen (not shown),a keyboard 151 (e.g. via a USB cable 153) and a mouse 152 (e.g. via aUSB cable 154), each of the keyboard 151 and the mouse 152 beingoperable by the user 170.

According to implementations of the present technology, the solid-statedrive 120 stores program instructions suitable for being loaded into therandom access memory 130 and executed by the processor 110 and/or theGPU 111 to operate a configuration platform. For example, the programinstructions may be part of a library or an application.

In FIG. 2, there is shown a networked computing environment 200 suitablefor use with some implementations of the present technology. Thenetworked computing environment 200 comprises a first electronic device202 and a second electronic device 209. Each of the first electronicdevice 202 and the second electronic device 209 may also be referred toas a “client device”, an “electronic device” or an “electronic deviceassociated with the user”. Each of the first electronic device 202 andthe second electronic device 209 may be associated with users. For thepurpose of illustrating the present technology, the first electronicdevice 202 is associated with an administrator of the configurationplatform 260 (i.e., a platform administrator) and the second electronicdevice 209 is associated with a person using the configuration platform260 so as to configure and render a configuration of a given product(i.e., a customer interfacing user). As an example, the customerinterfacing user may be a person acting on behalf of a product OEMengaged in a relationship with a customer, a person acting on behalf ofthe customer and/or the customer herself/himself. As an example, theplatform administrator and/or the customer interfacing user may be theuser 170.

Even though reference is made to a platform administrator, the term“administrator” should be broadly construed as an individual having abroader access to the configuration platform 260 than the customerinterfacing user so as to be able to “administrate” the configurationplatform 260. Also, even though reference is made to a customerinterfacing user, the term “user” should be broadly construed as anindividual using the configuration platform 260 so as to configure andrender configuration of a given product.

It should also be noted that the fact that the first electronic device202 and the second electronic device 209 are respectively associatedwith the platform administrator and the customer interfacing user, itdoes not need to suggest or imply any mode of operation—such as a needto log in, a need to be registered or the like.

The implementation of the first electronic device 202 and the secondelectronic 209 is not particularly limited, but as an example, the firstelectronic device 202 and the second electronic 209 may be implementedas a personal computer (desktops, laptops, netbooks, etc.), a wirelesscommunication device (a cell phone, a smartphone, a tablet and thelike), a virtual reality device or an augmented reality device. Thefirst electronic device 202 and the second electronic 209 may eachcomprise hardware and/or software and/or firmware (or a combinationthereof), as is known in the art, to execute an application 204.Generally speaking, the purpose of the application 204 is to enable aplatform administrator and/or a customer interfacing user to executevarious functions relating to managing settings of the configurationplatform and/or controlling the configuration platform so as to renderand configure a given product. To that end, the application 204comprises various graphical user interface (GUI) elements which arediscussed in greater details in the paragraphs below.

How the application 204 is implemented is not particularly limited. Oneexample of the application 204 may be embodied in the platformadministrator and the customer interfacing user accessing a web siteassociated with a configuration platform. For example, the application204 can be accessed by typing in an URL. It should be expresslyunderstood that the application 204 can be accessed using any othercommercially available or proprietary Internet browser (such as, but notlimited to, Chrome™ from Alphabet Inc., Internet Explorer™ fromMicrosoft Inc., Safari™ from Apple Inc.).

In alternative non-limiting embodiments of the present technology, theapplication 204 may be implemented as a dedicated application running onthe first electronic device 202 and/or the second electronic device 209.In such embodiments, the application 204 may be referred to as a “clientapplication” and the configuration platform 260 as a “serverapplication”.

In alternative non-limiting embodiments of the present technology wherethe first electronic device 202 or the second electronic device 209 isimplemented as a portable device, the first electronic device 202 or thesecond electronic device 209 may be an “app” available on an app storesuch as the App Store™ from Apple. It should be expressly understoodthat any other commercially available or proprietary browser applicationor any available or proprietary app can be used for implementingnon-limiting embodiments of the present technology.

The first electronic device 202 and the second electronic device 209 maybe coupled to a communications network 214 via a communication link (notshown). In some embodiments, the first electronic device 202 is directlyconnected to the configuration platform (for example, via an Intranet orvia direct physical connection to the configuration platform). In somenon-limiting embodiments of the present technology, the communicationsnetwork 214 can be implemented as the Internet. In other embodiments ofthe present technology, the communications network 214 can beimplemented differently, such as any wide-area communications network,local-area communications network, a private communications network andthe like.

How the communication link (not shown) is implemented is notparticularly limited and will depend on how the first electronic device202 or the second electronic device 209 is implemented. Merely as anexample and not as a limitation, in those embodiments of the presenttechnology where the first electronic device 202 or the secondelectronic device 209 is implemented as a wireless communication device(such as a tablet), the communication link (not shown) can beimplemented as a wireless communication link (such as but not limitedto, a 3G communications network link, a 4G communications network link,a Wireless Fidelity, or WiFi® for short, Bluetooth® and the like). Inthose examples, where the first electronic device 202 or the secondelectronic device 209 is implemented as a notebook computer, thecommunication link can be either wireless (such as the WirelessFidelity, or WiFi® for short, Bluetooth® or the like) or wired (such asan Ethernet based connection).

It should be expressly understood that implementations for the firstelectronic device 202 or the second electronic device 209, thecommunication link (not shown) and the communications network 214 areprovided for illustration purposes only. As such, those skilled in theart will easily appreciate other specific implementational details forthe first electronic device 202 or the second electronic device 209, thecommunication link (not shown) and the communications network 214. Assuch, by no means, examples provided herein above are meant to limit thescope of the present technology.

Also coupled to the communication network 214 is the configurationplatform 260. In some embodiments, the configuration platform 260 may beenabled by one or more servers 240, 242 and 244. The servers 240, 242,244 can be implemented as conventional computer servers. In an exampleof an embodiment of the present technology, the servers 240, 242, 244can be implemented as Dell™ PowerEdge™ Servers running the Microsoft™Windows Server™ operating system. Needless to say, the servers 240, 242,244 can be implemented in any other suitable hardware and/or softwareand/or firmware or a combination thereof. In the depicted non-limitingembodiment of present technology, the servers 240, 242, 244 define adistributed architecture relying on multiple servers. In alternativenon-limiting embodiments of the present technology, the functionality ofthe servers 240, 242, 244 may be on a single server.

Overall Platform

One or more of the servers 240, 242, 244 operates a configurationplatform 260. In the illustrated example of FIG. 2, the configurationplatform 260 comprises a client side application 270 and a ContentManagement System (CMS) 220. In the embodiment illustrated at FIG. 2,the client side application 270 comprises multiple software modules,namely, a 3D engine 272, a synchronization manager 273, a seatconfiguration engine 274, a rule engine 275, metadata translators 276and a project manager 277. The CMS 220 comprises multiple softwaremodules, namely, a conversion pipeline 221, a master data architecturemodule 222, a material bridge 223, a material library 224, a rulesauthoring module 225, a material library database 224, a projectsdatabase 226, a super Bill Of Material (BOM) database 227 and a superBill Of Material (BOM) metadata database 228. The conversion pipeline221 may access a Knowledge Base Engineering (KBE) database 231. Themaster data architecture module 232 may access a master data database232. The material bridge 223 may access a materials database 233. Moredetails relating to the various software modules of the client sideapplication 270 and the CMS 220 will be provided in the paragraphsbelow.

The general purpose of the configuration platform 260 is to allow,amongst other functionalities, a platform administrator and/or acustomer interfacing user to (1) generate real-time rendered visualresults of a configuration of a product (such as an aircraft cabininterior and/or an aircraft exterior); (2) provide remote control of theconfiguration of the product which may comprise operating theconfiguration platform remotely without server connectivity; (3)leverage engineering data for the purpose of real-time rendering andreal-time configuration of the product; (4) apply configurations rulesand/or (5) propagate a given customization associated with a givenelement of the product (such as a monument or a seat in the case of aconfiguration of an aircraft cabin interior) to other monuments sharinga same monument category.

As it will be understood by a person skilled in the art of the presenttechnology, software modules illustrated at FIG. 2 are provided as anexample and many variations may be therefore envision without departingfrom the scope of the present technology. This aspect should not beconstrued as being limitative of the scope of the present technology.

In the exemplified embodiment, the 3D engine 272 (which may equally bereferred to a 3D rendering engine or a 3D real-time engine) allows 3Drendering of polygon meshes in real-time meaning that a user mayvirtually move and/or manipulate 3D objects in real-time via theconfiguration platform 260. As an example, a user may virtually moveinto an aircraft cabin interior and/or change a line of sight whilemoving into the aircraft cabin interior. In some embodiments, the 3Drendering is rendered from a first-person point of view which allowsintuitively represent a cabin interior as if the user was virtually inthe rendered aircraft cabin interior. In some embodiments, the 3Drendering provides a fully immersive environment based on real-timecalculations of lighting, reflections and shadows. In some embodiments,the 3D rendering may be rendered on a regular 2D display, a 3D displayand/or a virtual/augmented reality headset so to provide a user with avisual experience of how she/he would perceive a given configuration ofthe aircraft cabin interior in real-life. In some embodiments, the 3Dengine 272 is the Unreal Engine™ game engine from Epic Games Inc. Othergame engines may equally be used without departing from the scope of thepresent technology.

In some embodiments the configuration platform 260 may be described as asystem for operating a configuration platform. The system may comprise aconversion pipeline (such as the conversion pipeline 221), a contentmanagement system (such as the CMS 220) and a 3D real-time engine (suchas the 3D engine 272). In some embodiments, the conversion pipelineallows converting a first set of data associated with a computer-aideddesign (CAD) system into polygon meshes suitable for rendering of theportion of a monument and configuration data, the configuration datacomprising at least one of a positioning of the monument, a materialsurface associated with the monument, a material grain directionassociated with the monument, lighting associated with the monument,annotations associated with the monument, alternate states associatedwith the monument and a kinematic sequence associated with the monument.

In some embodiments, the content management system stores the polygonmeshes and the configuration data. In some embodiments, the 3D real-timeengine allows to determine, based on the configuration data, at leastone of the positioning of the monument, the material surface associatedwith the monument, the material grain direction associated with themonument, the lighting associated with the monument, the annotationsassociated with the monument, the alternate states associated with themonument and the kinematic sequence associated with the monument; and torender the portion of the monument by the 3D real-time engine.

In some embodiments, the system comprises a material bridge (such as thematerial bridge 223), the material bridge being configured to accessparameters defining a property of a material, the parameters beingreflective of at least one of a finish type associated with thematerial, a scale associated with the material, a position associatedwith the material, a position associated with the material and aposition associated with the material; define applicability of theparameters to the monument; and assign, based on the definedapplicability of the parameters to the monument, a component identifierto the monument data and to other monuments data based on a relationshipbetween the monument data and the other monuments data.

In some embodiments, the system further comprises a rule engine (such asthe rule engine 275), the rule engine being configured to: accessconfiguration rules data, the configuration rules data modeling internalmonument configuration rules and external monument configuration rules,the internal monument configuration rules relating to an internalconfiguration of the monument affecting the monument and the externalmonument configuration rules relating to an external configuration ofthe monument affecting an environment in which the monument is to berepresented; apply at least a subset of the configuration rules data tothe monument data; and render the monument by the 3D real-time engine,the rendering being based on the internal configuration rules and theexternal configuration rules to represent the portion of the monument.

In some embodiments, the system comprises a configuration engine (suchas the seat configuration engine 274), the configuration engine beingconfigured to propagate a configuration setting of a 3D model to other3D models, the 3D model and the other 3Ds being part of a same 3D modelcategory.

Even though the configuration platform 260 may be used in connectionwith the configuration of multiple types of products (e.g., a vehicleinterior such as a car, a boat, a train, a building interior and thelike), the embodiments set forth in the paragraphs below illustratesconfiguration of an aircraft cabin interior. It should be understoodthat these embodiments are provided as an example and should not beconstrued as being limitative.

Example of an Aircraft Cabin Interior

Turning now to FIG. 3, an example of an aircraft cabin interior 300 isprovided. As a person skilled in the art may appreciate, the aircraftcabin interior 300 illustrates a cabin interior of a business aircraft,such as, but without being limitative, a Global 7000™ from BombardierInc. The aircraft cabin interior 300 extends longitudinally from anentry area 301 of the aircraft to a rear section 337 of the aircraft.The aircraft cabin interior 300 is divided in multiple zones, namely afirst zone 310, a second zone 320 and a third zone 330. According toembodiments of the present technology, a “zone” may be defined as asection of the aircraft cabin that extends from a first position to asecond position. In some embodiments, the first position is defined as aposition of a first bulkhead and the second position is defined as aposition of a second bulkhead. In some embodiments, the first bulkheadand the second bulkhead may be referred to as “zone dividers” as theyphysically divide volumes of the aircraft cabin interior 300 so as tocreate a visual impression of multiple “areas” or “rooms” through theaircraft cabin. As it may be appreciated by the person skilled in theart of the present technology, bulkheads may have multiple shapes anddimensions.

Referring back to FIG. 3, the first zone 310 extends from the entry area301 to a first bulkhead 312. Amongst other elements, the first zone 310comprises a seat 311. The second zone 320 extends from the firstbulkhead 312 to a second bulkhead 331. The second zone 320 comprises aset of seats 321, 322, 323 and 324 and a table 325. The second zone 320also comprises a second set of double seats 326 and 327, a credenza 328and a table 329. Reference is made to “double seat(s)” so as to conveythe notion of two individual seats merged into a single structural unit.In some embodiments, the second zone 320 may be referred to as a “doublezone” as it spreads across a volume of two “single zones” (such as thethird zone 330). In the illustrated embodiment, the second zone 320 mayaccommodate eight passengers during take-off and landing of theaircraft. The third zone 330 extends from the second bulkhead 331 to athird bulkhead 336. The third zone 330 comprises a set of seats 332 and335, a table 334 and a divan 333. In the illustrated embodiment, thethird zone 330 may accommodate four passengers during take-off andlanding of the aircraft.

Turning now to FIG. 4, a top plan view of an aircraft cabin interior 400is represented. In the illustrated embodiment, the representation of theaircraft cabin interior 400 is taken from a screenshot illustrating anembodiment of a Graphical User Interface (GUI) component provided by theconfiguration platform 260 to a user of the configuration platform 260(such as a platform administrator or a customer interfacing user). Insome embodiments, the GUI component allows the user of the configurationplatform 260 to select a configuration for each one of the zones of theaircraft cabin interior and/or configure one or more elements of eachone of the zones of the aircraft cabin interior. The one or moreelements may comprise seats, tables, monuments (e.g., credenza), divans,beds and the like.

The aircraft cabin interior 400 comprises four zones, namely a firstzone 410, a second zone 420, a third zone 430 and a fourth zone 440. Thefirst zone 410 comprises a first set of seats 411, 412, 413 and 414, afirst table 415 and a second table 416. The second zone 420 comprises aset of single seats 421, 424, a set of double seats 422, 423 and tablecomprising two sections 425, 426 that may be configured to form a singleconference table accommodating six passengers. The third zone 430comprises a first divan 431 and a second divan 432. Each one of thefirst divan 431 and the second divan 432 may accommodate up to sixpassengers during take-off and landing. The fourth zone 440 comprises afirst credenza 441, a second credenza 443 and a double bed 442.

Turning now to FIG. 5, a screenshot 500 illustrates an embodiment of aGUI provided by the configuration platform 260 to the user of theconfiguration platform 260. The screen shot 500 comprises three GUIcomponents, namely a first GUI component 510, a second GUI component 520and a third GUI component 530. In the illustrated embodiment, the firstGUI component 510 is a horizontal scrolling menu allowing the user toselect a specific layout for a given zone of the aircraft cabininteriors. Various examples of layouts 511-518 are illustrated showingmultiple combinations of seats, tables, credenzas, beds and divans. Thesecond GUI component 520 illustrates a current configuration of anaircraft cabin interior which the user may modify by dragging anddropping one or more layouts 511-518 into the second GUI component 520.The aircraft cabin interior illustrated in the second GUI component 520is similar to the aircraft cabin interior illustrated in FIG. 4 with afirst zone 522 corresponding to the first zone 410, a second zone 524corresponding to the second zone 420, a third zone 526 corresponding tothe third zone 430 and a fourth zone 528 corresponding to the fourthzone 440. The third GUI component 530 provides the user with the abilityto switch from one configuration screen to another. In the illustratedembodiment, the user may switch from “floorplan” (current selectionrepresenting the first GUI component 510 and the second GUI component520) to “equipment & furnishing”, “design” and/or “exterior”.

Example of a GUI

Turning now to FIG. 6, a screenshot 600 illustrates an embodiment of aGUI provided by the configuration platform 260 to the user of theconfiguration platform 260. The screen shot 600 comprises the first GUIcomponent 510 of FIG. 5, the second GUI component 520 of FIG. 5 and thethird GUI component 530 of FIG. 5. In the embodiment illustrated in FIG.6, only the first zone 522, the third zone 526 and the fourth zone 528are selected while the second zone 524 is left blank. In someembodiments, the user may select a layout from the first GUI component510 and drag and drop it into the second GUI component 520, for example,so as to populate the second zone 524 with a selected layout. Also shownin FIG. 6 is an aircraft cabin interior layout selector 700. Anembodiment of the aircraft cabin interior layout selector 700 isillustrated in FIG. 7. Multiple cabin layouts 701-707 are illustratedwith a currently selected cabin layout being 702. As it may beappreciated by the person skilled in the art of the present technology,various configurations are associated with one or more digits, eachrepresenting a number of passengers during take-off or landing in agiven zone. As an example, the cabin layout 701 is associated with thelayout “4-4-4” meaning that the selected layout is made of three zones,each spanning four windows in length. Other examples of cabin layoutsare also represented by the cabin layouts 702-707.

Turning now to FIG. 8, a 3D rendering 800 of an aircraft cabin interioris illustrated. The 3D rendering 800 represents a given configuration820 generated by 3D engine 272 of the configuration platform 260 whichcomprises a first sideledge 821 and a second sideledge 825, a first seat822, a second seat 823, a pair of rear seats 827, a divan 826, abulkhead 830 and a floor 824. The 3D rendering 800 also comprises a GUIcomponent 810 similar to the third GUI component 530 of FIG. 5. In someembodiments, the 3D rendering is rendered in real-time meaning that auser may virtually move into the aircraft cabin interior and/or change aline of sight. In some embodiments, the 3D rendering is rendered from afirst-person point of view which allows intuitively represent a cabininterior as if the user was virtually in the rendered aircraft cabininterior. In some embodiments, the 3D rendering is generated by a 3Dengine such as the 3D engine 272 described in connection with FIG. 2. Insome embodiments, the 3D rendering provides a fully immersiveenvironment based on real-time calculations of lighting, reflections andshadows. In some embodiments, the 3D rendering may be rendered on aregular 2D display, a 3D display and/or a virtual/augmented realityheadset so to provide a user with a visual experience of how she/hewould perceive a given configuration of the aircraft cabin interior inreal-life.

Additional Software Modules

Turning now to FIG. 9, various additional software modules that may beimplemented by the configuration platform 270 are illustrated. In theillustrated embodiment, the various software modules comprise anadministrator module 900, a master data catalog 910 and a miscellaneoussettings module 920. In some embodiments, the administrator module 900may only be accessible by a platform administrator and may allowexecution of one or more of a user manager module 902 which may be partof the project manager module 277, a project manager module 904 whichmay be part of the project manager module 277 and a documentation andreports module 906. In some embodiments, the user manager module 902 mayallow to manage access rights to the configuration platform 270. In someembodiments, the project manager module 904 may allow to manage, store,restore and/or render aircraft cabin interior configurations partiallyor completely defined by one or more users which may be stored in theprojects database 226. In some embodiments, the documentation andreports module 906 may allow generation of documentation and reportsassociated with one or more aircraft cabin configurations. In someembodiments, the generated documentation and reports may be used forpresenting information to a client, support the engineering and themanufacturing of a given aircraft cabin interior configuration and/orpresenting information to certification authorities.

In the illustrated embodiment, the master data catalog module 910 may beimplemented via the master data architecture module 222, the materialbridge 223, the master data 232, the materials database 233 and/or thematerial library database 224. The master data catalog module 910 maycomprise a 3D pipeline 911 (which may be implemented by the conversionpipeline 221), a floorplan catalog 912, an inner options and equipmentcatalog 914, a paint scheme catalog 916, a materials/finishes catalog917 and a validation module 918. Each one of the floorplan catalog 912,the inner options and equipment catalog 914, the paint scheme catalog916, the materials/finishes catalog 917 may store data relating toavailable configurations of various elements of the aircraft and/or ofthe associated cabin interior. In some embodiments, the validationmodule 918 may allow to control and/or validate one or more combinationsof configurations selected from one of the floorplan catalog 912, theinner options and equipment catalog 914, the paint scheme catalog 916,the materials/finishes catalog 917.

In the illustrated embodiment, the miscellaneous settings module 920comprises a marketing material module 922 and a GUI updates module 924.In some embodiments, the marketing material module 922 and the GUIupdates module 924 may only be accessible by certain categories of users(e.g., platform administrator). The marketing material module 922 mayallow generating marketing material based on one or more aircraft cabininterior configurations. The GUI updates module 924 may allow updatingone or more aspects of the GUI components that are presented to a userof the configuration platform 270.

Turning now to FIG. 10, a flowchart 100 illustrates a sequence of stepsthat may be presented to a user of the configuration platform 270 so asto generate one or more configurations of a product (such as an aircraftand its associated cabin interior). In the illustrated embodiment, afirst step 1002 aims at creating and/or launching a session with theconfiguration platform 270. Then a second step 1004 aims at capturinginformation relating to a country of certification and/or otherpreliminary information. In some embodiments, the captured informationrelating to the country of certification may impact how certain rulesare applied during the various steps of the configuration so as toensure that a generated configuration complies with the regulations ofthe selected country of certification. A user may then select to proceedto a third step 1006 and/or a fourth step 1008. In some embodiments, thethird step 1006 may prompt the user to complete a selection of a 2Dfloor plan (so at to complete a 2D floor plan configuration such as theone illustrated at FIG. 4). In some embodiments, the fourth step 1008may propose pre-stored 2D floor plan selections to the user. The fourthstep 1008 may then proceed to a fifth step 1010 which allow a styleselection.

In some embodiments, further to a completion of steps 1006 or 1010,steps 1012-1018 may be executed. In some embodiments, the sixth step1012 may allow the user to proceed to a selection of 3D material, theseventh step 1014 may allow the user to proceed to a selection of 3Dinner option, the eighth step 1016 may allow the user to select a 2Dfurnishing and equipment and a ninth step 1018 may allow the user toconduct a static walkthrough of a representation of the aircraft and/oraircraft cabin interior. In some embodiments, steps 1020 and 1022 may beexecuted. Step 1020 may allow a 3D representation of an aircraftexterior paint. Step 1022 may allow generation of a session summaryand/or other outputs.

Turning now to FIG. 11 to FIG. 15, various aspects of the presenttechnology will be described.

Monument Levels

As detailed in the background section of the present document, cabininteriors of business aircraft may be extensively customizable. Eachcabin interior may be purpose-built to suit customers' requirements andpreferences. In some embodiments of the present technology, avariability of customization may be defined in terms of monuments. Insome embodiments, a monument may be defined as self-contained elementswhich may collectively make up an aircraft cabin interior. In someembodiments, a monument may comprise structural elements such as, butnot limited to, sidewalls, sideledges, bulkheads. In some embodiments, amonument may comprise furniture such as, but not limited to, seats(single seats, double seats), divans, credenzas, cabinets, beds. In someembodiments, a monument may comprise functional elements such as, butnot limited to, galleys and/or toilets.

Customizability (equally referred to configurability) of monuments maycomprise disposition of the monuments within the aircraft cabin as wellas an internal configuration of the monuments. In some embodiments, aconfiguration of a monument may be defined at multiple levels. As anexample, a first level may be a monument envelope, a second level may bea configuration zone and a third level may be a design feature.

Regarding the first level, each monument envelope being associated witha given variation of the monument. For example, a front face of acredenza may be flat, curved inboard or curved outboard. In someembodiments, a choice of monument envelope for a monument may affectsome or all of the components of the monument.

Regarding the second level, monuments may be divided into configurationzones, each of which may be customized. As an example, a credenza of acabin interior of a Global 7000™ from Bombardier Inc. comprises threeenvelopes and three configuration zones, one of which determines thepresence or absence of shelves.

Regarding additional third level customization, the design features andtheir respective configurations may comprise customizabledecorative/aesthetic elements such as inlays, different shapes oflatches and the like.

Conversion Pipeline

In accordance with some aspects of the present technology, a conversionpipeline may support input documents in Catia format (e.g., .CATPartand/or .CATProduct file extensions associated with Catia V5™ fromDassault Systems). In some embodiments, the conversion pipeline isimplemented by the conversion pipeline 221. As a person skilled in theart of the present technology may appreciate, Catia documents may benested—e.g., a document contained in one file may include, by reference,a sub-document contained in a different file. Input files for aconversion pipeline in accordance with the present technology maycontain one or more KBE collectors. In some embodiments, the KBEcollectors may be basic collectors (also referred to as “COL”) orstandard part collectors (also referred to as “SP”). In someembodiments, each one of the KBE collectors may contain 3D geometryand/or metadata about different characteristics of the part. In someembodiments, each one of the KBE collectors may be identified by aspecific naming convention.

In some embodiments, basic collectors may generally contain arepresentation of the large-scale structure of a monument, as anexample, but without being limitative, panels making up drawers, doors,cushions and the like. An example of naming convention may be asfollows: C350-79-000COLL01, which may translate into collector #01 frommonument 79 of the Challenger 350™ dataset.

In some embodiments, standard part collectors may generally contain arepresentation of structural hardware (also referred to as accessories)associated with a monument, as an example, but without being limitative,hinges, latches, handles and the like. An example of naming conventionmay be as follows: GXRS0000-0000-14-000SP05, which may translate into SPcollector #05 from monument 14 of the Global 6000™ dataset.

Each collector is required to have a “definition” metadata attribute todefine it as an element of the monument's configurability as well as itsrelationship to other collectors which make up the monument. In someembodiment, the definition attribute may be an alphanumeric string,prefixed with “COL_” or “SP_” depending on the collector type and may beunique for a given aircraft dataset. In some embodiments, a format maybe associated with each one of an envelope collector, a zoneconfiguration collector and a design feature collector. In the followingexamples, alphanumeric character or decimal digit are replaced by either@ sign or # sign.

As a first example, “M@@ S##” may define an envelope collector. The twocharacters @@ following the “M” may identify a monument number to whicha collector belongs. The two digits following the “S” may identify anenvelope number within a specified monument. In some embodiments, anenvelope collector may contain 3D geometry applicable to a configurationof a monument when a corresponding envelope is selected as an option,independently of any choices of configuration zones or design features.For example, in the Global 6000™ dataset, “COL_M01 S02” may be a basiccollector for an inboard-curved envelope (S02) of a credenza monument(M01).

As a second example, “M@@ S## Z## C##” may define a zone configurationcollector which may contain information about a specific configurationoption available for one of the monuments' zones. As for the envelopecollector described in the paragraph above, the two characters following“M” and “S” identify a corresponding monument and envelope. A “Z” numbermay identify a zone and a “C” number may identify a configuration optionwhich the collector may define, one of several that may be available fora particular zone. Pursuing with the example of the Global 6000™credenza, “COL_M01 S02 Z02 C01” may be the basic collector of a shelfoption (C01) for a mid-compartment zone (Z02) within an inboard-curvedenvelope (S02) of a credenza monument (M01). As an example, otherconfigurations available in a given zone (Z02) may be drawers “COL_M01S02 Z02 C03” or a minibar , “COL_M01 S02 Z02 C04”.

As a third example, “M@@ S## D## C##” may define a design featurecollector which may be semantically similar to a zone configurationcollector but may define an option for a design feature rather than azone. The “D” number may identify a design feature and the “C” numbermay identify an option for that design feature to which the collectorpertains. Pursuing with the example of the Global 6000™ credenza,“COL_M01 S02 D28 C01” may be a basic collector of a vertical oval option(C01) for latches (D28) within the inboard-curved envelope (S02) of thecredenza monument (M01). Other latch shapes available may be horizontaloval (COL_M01 S02 D28 C02), square (COL_M01 S02 D28 C03) or round(COL_M01 S02 D28 C04).

Collector Cross-Dependencies

In some embodiments, a content of a zone configuration collector or adesign feature collector may depend not on only on a configurationchoice for a particular part of the monument, but also a choice forother zone and/or design feature of the monument. In such a case,definitions for both of the interdependent collectors may be modifiedaccording to one of two conventions, namely a single cross-dependenciesconvention and a multiple cross-dependencies convention.

Single Cross-Dependencies

As a first example, “M@@ S## Z## C##” or “M@@ S## D## C##” may define azone configuration collector or a design feature collector which mayhave an impact on collectors for one or more options elsewhere in themonument's configuration. As a second example, “M@@ S## Z## C##” or “M@@S## D## C##” may define a zone configuration collector or a designfeature collector which may be subordinate to a configuration choice foranother part of the monument.

When a monument is configured such that it contains a collector with anX number suffix, any collectors with a Y number suffix also present inthe monument configuration are subordinate and must be selected suchthat the Y numbers match the X numbers. As an example, a Challenger 350™galley may be configured with a drip tray or a full sink (for thebaseline envelope, collectors COL_M03 S01 Z07 C01 X08 and COL_M03 S01Z07 C02 X09 respectively). This has an impact on the construction of themonument's façade design feature (D32), which must therefore beavailable in two separate collectors: COL_M03 S01 D32 C01 Y08 andCOL_M03 S01 D32 C01 Y09.

A collector named following this “single” configuration may only be usedto identify a single cross-dependency. In some embodiments modeling anaircraft cabin interior, no multiple cross-dependencies exist.

Multiple Cross-Dependencies

In some other embodiments, a dataset may contain monuments where ageometry of a particular collector depends, besides its own specificconfiguration, on configuration choices for multiple other zones ordesign features. In such a case, a more flexible naming convention maybe used. A subordinate collector may be identified with a definitionmatching “M@@ S## Z## C## [Z## C##]”, “M@@ S## Z## C## [Z## C##] [Z##C##]”, etc. A bracketed portion of the definition may identify aparticular configuration for each of an arbitrary number of differentconfiguration zones, each of which impacts the choice of the subordinatecollector. Note that although configuration zones (the “Z” prefix) areused here for simplicity's sake, the subordinate collector or any of itsdependencies may also be design features (“D” prefix) or “A”/“B”configurations (see the “Alternate States” section below).

Physical Geometry

Physical objects within Catia documents may be represented by entitiescalled “bodies”. Any bodies within an input document processed by theconversion pipeline 221 may be converted to polygon meshes (alsoreferred to as tessellated models) for use in a 3D rendering engine,such as the 3D engine 272. A level of fidelity when converted parametricsurfaces, such as, for example, Non-Uniform Rational Basis Splines(NURBS) to polygon meshes may be configurable. In some embodiments,there might be a need to find a suitable trade-off between (1) visualquality, which is better with high-polygon meshes and (2) frame rate,which improves when a number of polygons is lowered.

In some embodiments, each body entity may be associated with a name,which may be used for identifying metadata associated with the body. Insome embodiments, how names may be determined may depend on a collectortype.

In some embodiments, for basic (i.e., non-SP) collectors, a name may bethat of a body node itself, but may have a KBE prefix which may bestripped to match associated metadata. For instance, if a body iscontained within a node identified as “BI_KBE_M03_Panel_BI001”, thebody's name may be “M03_Panel_BI001”. It may then be matched with ametadata key of “ATB_M03_Panel_BI001”. The prefix of the node name mayconform to a pattern “{A . . . }_KBE”, where {A . . . } may be a stringof letters of arbitrary length. In addition, a name of the body node maybe referenced from one of the component's parameter nodes: a parameternode may exist which may have a string value of the form “{BodyName}COL##”, where the suffix digits may correspond to a number of thecollector (as reflected in its filename). Following the earlier example,a body contained in a node identified as “BI_KBE_M03_Panel_BI001” incollector C350-03-000COL05 may only be processed if there exists aparameter node with a string value of “BI_KBE_M03_Panel_BI001 COL05”.

In some other embodiments, for SP collectors, the node name may notcontain a KBE prefix to be stripped out, but rather may be given a“VISUALIZE_” prefix. In addition, the node with the “VISUALIZE_” prefixmay be the parent of the actual physical geometry node (which typicallymay have an unrelated name such as ThickSurface.1, Assemble.7, etc.).Body nodes in SP collectors not matching this convention may be ignored.The “VISUALIZE_” prefix may not be stripped when matching metadata keys,for instance, the body name “VISUALIZE_Outlet” is matched with metadatanamed “ATB_VISUALIZE_Outlet”.

Materials and Projections

Along with the polygon mesh for a converted body node, the conversionpipeline 221 may convert the projection mapping for the materialassociated with the body in the input document. The projection mappingmay be defined in Catia™ using the material properties dialog 1102 asillustrated in the screenshot 1100 of FIG. 11. The screenshot 1100 alsoillustrates “material size” parameter 1104, “mapping” function 1106,“scale U/V” parameter 1108, “position U/V” parameter 1110 and“orientation” parameter 1112. One or more of the parameters/functions1104-1112 are used to calculate a UV mapping on a polygon mesh so as toensure that application of textures in the configuration platform 260matches the way in which they are rendered in Catia™. In someembodiments, restrictions may apply. As a first example, Catia™ mayprovide for six options for projective texture mapping, namely (1)planar, (2) spherical, (3) cylindrical, (4) cubic, (5) auto adaptive and(6) manual adaptive. In some embodiments, options (5) and (6) may no besupported by the conversion pipeline 221. As a second example, valuesfor “scale UN”, “position UN” and “orientation” may not be read directlyfrom the body's material properties. Rather, they may be expressed in“parameters” metadata nodes. There are two supported schemes fororganizing such nodes, namely “single-value” and “multiple-value”. Insome embodiments, should the value is not present in metadata nodes, thevalues default to 1.0 for scale and 0.0 for position and orientation. Asa third example, the actual texture image used in Catia™ is ignored,texture images used for rendering in the configuration platform 260 aremanaged separately in the CMS 220. In some embodiments, a transformassociated with a material (which may be indicated by a compass when thematerial node is selected) may affect a projection as well, it may betaken into account when generating the UV mapping. In some embodiments,the material's finish may be defined in a suitably-named metadata node.

Single-Value Metadata Convention for Material Parameters

In some embodiments, under this scheme, each parameter describing aproperty of materials application for a particular body entity may beexpressed separately as a value of a matching parameter node. Parametersnodes may be named with an “ATB_” prefix followed by a body name (e.g.,a name following conventions described above in connection with thedescription of the non-SP collectors and the SP collectors). In someembodiments, the following keys may be recognized: (1) MType: which maydefine a material's finish type and (2) MScale U, MScaleV, MPositionU,MPositionV, and MOrientation: which may be used instead of correspondingvalues in Catia's material properties (see FIG. 11).

As an example, for a non-SP collector body whose node may be named“AA_KBE_M01_Panel_W07_AA_F”, the body name (after stripping the KBEprefix) is taken to be “M01_Panel_W07_AA_F” and the associated parameternode names may be “ATB_M01_Panel_W07_AA_F_MType”,“ATB_M01_Panel_W07_AA_F_MScaleU” and so forth.

Multiple-Value Metadata Convention for Material Parameters

In some embodiments, under this scheme, all material parameters may beconcatenated together into a single parameter node using the “MType” key(prefixed with “ATB_” and the body name as above). The value string maybe a string which may be parsed as a pipe-separated list of recordtables, records and fields organized which may be organized as describedin the paragraph below.

An overall string value may be a list of record tables separated by astring “| | |”. Each table may be identified by its position in the listand the following may be relevant to materials properties, namely (0)Position 0: TypeFinish family name, (1) Position 1: default material toapply, (2) Position 2: applicable materials and (3) Position 3:component type. Each record table may be a list of records separated bya string “| |”. Each record may be a list of key-value pairs separatedby the string “|” between pairs, the key and value may be separated bythe string “=”. The value may be optional, when no “=” is present thekey may be considered to have no associated value. For example, a recordmay be found in table 1 (default materials): “TypeFinish007 |Description=Plated | Color007=#CBCECA | Orientation=0deg”.

In some embodiments, the material finish type and all mapping parameters(ScaleU, ScaleV, PositionU, PositionV and Orientation) may be found intables at position 1 (default material) and 2 (full list of applicablematerials). In some embodiments, the “M” prefix present in thesingle-value parameters above (MScaleU, MOrientation) may not be used.

Positions Identifiers (PIDs)

In some embodiments, to place a monument at its intended location withina 3D scene generated by the 3D engine 272, the configuration platform260 may refer to a set of positions and/or orientation coordinates.These coordinates may be associated with a naming convention that may bereferred to as “Positions Identifier” or PIDs. Whereas some monumentsmay only be place at a single position in the aircraft cabin,irrespectively of any configuration choices, others (e.g., seats) may bepresent at multiple positions. Two conventions may be used to define anavailable position or positions that a monument may occupy. In allcases, PIDs may be defined for each of the monument envelopes so thatzone and design feature collectors may be positioned using the PIDselected for the corresponding envelope collector. A first conventionmay be referred to as “aircraft origin”. A second convention may bereferred to as “PID axis systems”.

Referring to the first convention, for single-position monuments, anallowable set of coordinates may be identified by a nested Catiadocument with a special name “AIRCRAFTORIGINPART-KBE”. The coordinatesof this “virtual part” may be considered to be the point of referencefrom which an offset to the monument origin may be calculated. In aninput document structure, such as the input document structure 1200illustrated at FIG. 12, it may be a sibling to the monument'scollectors. In other words, references to an origin part and themonument collectors may be placed in a same container document as in theexample of FIG. 12.

Referring to the second convention, for multiple-position monuments,each set of allowable coordinates may be identified by an “axis system”node in the Catia document. Each node representing a PID may be namedwith a prefix “DATUM_AXIS_PID_” followed by the PID code itself. PIDcodes may be globally unique across all monuments of all aircraftmodels.

Lights

Light fixtures in monuments may be defined by body nodes, located in theCatia document for the corresponding collector which may conform to aparticular naming convention. Matching nodes may not convert intopolygon meshes but rather as handled as a special case. These markernodes for lights may be present in either base collectors or SPcollectors and the naming convention may differ in two cases. First, fornon-SP collectors, the marker node may be named as follows:“ENV_M##_<light name>_Light<light type> Surface_MarkerForKBE”. Second,for SP collectors, the marker node may be named as follows:“ENV_Light<light type> Surface_MarkerForKBE”. “M##” may be a placeholderfor the monument number; <light name> may be a placeholder for thelight's identifying name and <light type> may be a place holder for oneof the three different supported types of light: “Spot” for spot lights,“Point” point lights and “Shape” for shaped lights.

The light's spatial parameters may be defined by several associated bodynodes which may be present along with the “Surface” marker node. Thenumber and nature of these complementary nodes may depend on the type oflight being defined.

Point Lights

Point lights project light in all directions from a single point inspace. An example 1302 is provided at FIG. 13. The marker surface mustbe a geometric body containing a sphere whose centre may be the pointfrom which light is emitted. No complementary nodes may be required forpoint lights. The only item of information which may be required is thelocation of a center of a sphere.

Shaped Lights

Like point lights, shaped lights emit in all directions. However, thesource is not a single point but rather a capsule shape. These lightstherefore behave in much the same way as a straight fluorescent tube. Anexample 1304 is provided at FIG. 13. The marker surface may be ageometric body containing a cylinder whose shape and position may matchthe “tube” from which light may be projected. No complementary nodes maybe required for point lights. The position, length and radius of thecylinder may be used for determining parameters of the light.

Spot Lights

Spot lights project a cone-shaped field of light from a single point inspace. The marker surface may be a geometric body node containing a conewhich may match a shape of a beam. An example 1306 is provided at FIG.13. The tip of the cone may mark a conceptual origin of the light fieldand may not be normally positioned at the location of a physical lightfixture itself. A complementary node, whose name may be prefixed withthe following string may be present (example is given for non-SPcollectors): “ENV_M##_<light name>_LightSpotCircle”. A geometric bodynode may contain a circle positioned to match the surface of a lightfixture to distinguish the actual physical source of the light from thetip of the cone.

Hotspots

Hotspots (also referred to as annotations), including annotation points,may be defined by body nodes, located in the Catia document for acorresponding collector which may conform to a particular namingconvention. Matching nodes may not have to be converted into polygonmeshes but rather may be handled as a special case. A single-point bodynode, whose name may begin with the prefix “ANN_” may be treated as ahotspot. There must also be a parameter node a matching name, used toindicate a type of hotspot. Hotspot type may be as follows. First,“C00_T01” and “C00_T02”. A point used to position a UI element specificto the monument, in order to provide means of performing various actionsor retrieving multimedia information (text, images, video) related to amonument. The two variants may be used for non-seat monuments (T01) andseats (T02). These hotspots may be present in envelope collectors.Second, “C01_T01” and “C01_T02”. A point used to position annotationcallouts within a monument in a utility view of the configurationplatform 260. The two variants may be used for outer monumentannotations (T01) and inner monument annotations (T02).

Alternate States

Certain monuments may be represented in more than one state or position.For instance, a divan may be berthed or deployed, galley drawers may beopen or closed. In some embodiments, a kinematic sequence is furtherassociated to allow real-time representation of a monument transitioningfrom a first state (galley drawers open) to a second state (galleydrawers closed). These are identified by an extension of the collectornaming convention, similar to the way configuration zones and designfeatures may be identified. When part of a monument exists in multiplestates, the affected geometry may be gathered into collectors withidentifiers matching the pattern “M## S## B## C##” or “M## S## A## C##”(the “B” initial may represent a “behaviour” of the monument). As it isthe case with configuration zones and design features, only one of theavailable collectors for a given behaviour may be present in the 3Dscene at any given time.

Special Cases

Collectors identified with a C01 configuration may be considered thedefault. They may be used in the main cabin view. Collectors whosepart-level “Nomenclature” metadata text may contain the word “Door”followed by the word “Hidden” correspond to the “hidden doors”configuration. They may be used in the utility view of the configurationplatform 260 to enable a user to see an inside of a monument's storagecompartment.

EXAMPLES

The Challenger galley has many instances of alternate states, so it maybe used in all the following examples. For simplicity's sake identifierswill be shortened to omit the “M03 S05” prefix. One of the simplestcases would be the tambour doors, which may be either closed or open.Therefore, there is one collector for the “closed” state, identified(without the M03 S05 prefix) as B26 C01, and a corresponding alternatecollector for the “open” state, identified as B26 C02.

When the resulting collectors are also affected by a configuration zonewith multiple options, the result is a part whose geometry varies infunction of several independent configuration choices, so that the X/Yidentifier suffix may be required. For instance, the configuration ofcertain drawers may be affected by whether the galley is configured witha sink or a drip tray (configuration zone Z07). The drawers may also beeither open or closed; there are therefore four different possiblestates of the drawer. This is represented by assigning an X suffix tothe sink/drip tray configuration zone, so that its two collectors becomeZ07 C01 X01 (sink) and Z07 C02 X02 (drip tray). That allows the drawergeometry to depend both on the Z07 configuration and the open/closedstate, by identifying the following collectors: B24 C01 Y01, closeddrawer when sink option is selected; B24 C01 Y02, closed drawer whendrip tray option is selected; B24 C02 Y01, open drawer when sink optionis selected; B24 C02 Y02, open drawer when drip tray option is selected.

The final example illustrates the case where the part involved in analternate state itself is a configuration zone. This differs from theprevious case because there is no separate configuration zone which canbe used as a basis for the X/Y suffix, so it may be necessary to createa placeholder collector with no geometry. Consider a drawer which may beconfigured with or without a pull-out work surface, and may also berepresented open or closed. The first two collectors below are thealternate state placeholders; the rest are the geometry collectorsrepresenting the four possible representations of the drawer: B03 C01X03, closed state placeholder; B03 C02 X04, open state placeholder; Z03C01 Y03, closed drawer without pull-out surface; Z03 C02 Y03, closeddrawer with pull-out surface; Z03 C01 Y04, open drawer without pull-outsurface; Z03 C02 Y04, open drawer without pull-out surface.

Turning now to FIGS. 14 and 15, examples of multiple levels ofconfiguration and collectors generated based on such configuration areillustrated. FIG. 14 illustrates a “Monument 01” 1402 which may havebeen accessed from the CMS 220. The “Monument 01” 1402 may be associatedwith a first 3D object 1404 and a second 3D object 1406.

FIG. 14 illustrates three levels of configurations, namely a monumentenvelope, a configuration zone and design features. In the illustratedexample, the “Monument 01” 1402 is associated with three monumentenvelopes 1412, 1414 and 1416. Each one of the monument envelope may beassociated with with a given variation of the monument. Each one of themonument envelopes 1412, 1414 and 1416 may be associated with one ormore configuration zones, such as the configuration zones 1422, 1423 and1424. Each one of the configuration zones may be associated with one ormore configurations. As an example, the configuration zone 1422 isassociated with “Configuration 01” 1432, “Configuration 02” 1433 and“Configuration 03” 1434. As another example, the configuration zone 1423is associated with “Configuration 01” 1435 and “Configuration 02” 1436.As another example, the configuration zone 1424 is associated with“Configuration 01” 1437 and “Configuration 02” 1438. In someembodiments, “Configuration 01” 1432, “Configuration 01” 1435 and“Configuration 01” 1437 are similar. In some embodiments, “Configuration02” 1433, “Configuration 02” 1436 and “Configuration 02” 1438 aresimilar.

In addition, to the monument envelope and the configuration zone, the“Monument 01” 1402 may be associated with a general design feature“Design Feature 20” 1410 and a local design feature “Design Feature 01”1425. The general design feature “Design Feature 20” 1410 may bereflective of a configuration that may apply independently of themonument envelope and/or the configuration zone while the local designfeature “Design Feature 01” 1425 may depend from the monument envelopeand/or the configuration zone. In the illustrated example, the generaldesign feature “Design Feature 20” 1410 is associated with“Configuration 01” 1430 and “Configuration 02” 1431 and the local designfeature “Design Feature 01” 1425 is associated with “Configuration 01”1440 and “Configuration 02” 1441.

FIG. 15 illustrates examples of data collectors associated with thefirst 3D object 1404 and the second 3D object 1406 of FIG. 14. A firstset of data collectors 1504 is associated with the first 3D object 1404and a second set of data collectors 1514 is associated with the second3D object 1406. In the illustrated embodiments, both the first set ofdata collectors 1504 and the second set of data collectors 1514 arestored into the Super BOM Library 227. In other embodiments, the firstset of data collectors 1504 and the second set of data collectors 1514may be accessed from a different database and/or directly accessed fromthe conversion pipeline 221. As can be seen, the first set of datacollectors 1504 is associated with a first monument envelope (Shape 01)of the “Monument 01” 1402 and comprises both basic collectors (e.g.,“S01 COLLECTOR COL01”, “S01 COLLECTOR COL Z01-C01”) and standard partcollectors (e.g., “S01 COLLECTOR SP01”, “S01 COLLECTOR SP Z01-C01”). Inthe illustrated example of FIG. 15, the second set of data collectors1514 is associated with a second monument envelope (Shape 02) of the“Monument 01” 1402 and comprises both basic collectors (e.g., “S02COLLECTOR COL01”, “S02 COLLECTOR COL Z01-C01”) and standard partcollectors (e.g., “S02 COLLECTOR SP01”, “S02 COLLECTOR SP Z01-C01”).

Rules Application

Turning now to FIG. 16, embodiments of rule formats 1602 and 1606 and arule example 1604 are provided. In some embodiments, the rule formats1602 and 1606 may be relied upon to execute a method of applyingconfiguration rules while operating the configuration platform 260. Insome embodiments, execution of the method of applying configurationrules may be executed by the rule engine 275. In some embodiments, rulesand/or rule formats may be edited via the rules authoring module 225. Insome embodiments, rules, stored as configuration rules data inaccordance with rule formats (such as, but not limited to, the ruleformats 1602 and 1606), may be accessed. The configuration rules datamodel internal monument configuration rules and external monumentconfiguration rules. In some embodiments, the internal monumentconfiguration rules may relate to an internal configuration of themonument affecting the monument itself. In some embodiments the externalmonument configuration rules may relate to an external configuration ofthe monument affecting an environment in which the monument is to berepresented. Once accessed, the configuration rules data may then beapplied, for example by the rule engine 275, to a monument before beingrendered by the 3D engine 272 so as to present a visual representationof the monument which takes into consideration the various configurationrules. As an example, a divan positioned in a vicinity of an exit doormay trigger a configuration rule which require a particularconfiguration of the divan to be selected and/or represented. Theparticular configuration of the divan may comprise specific features(such as a removable backrest) compatible with the position of the divanin front of the exit door.

As a first example, the rule format 1602 is structured in a three foldslogic structure, namely “IF:-- THEN:-- IS: --”. The rule example 1604illustrates an example of a rule structured in accordance with the ruleformat 1602. The rule example 1604 allows defining whether certainoptions, monuments and/or design features are inherent, mandatory, notavailable or optional. As an example, but without being limitative, therule example 1604 may model a rule according to which IF: “ZONECONFIGURATION = 02”, THEN: “DIVAN”, IS: “MANDATORY”. This example maytranslate as if zone configuration=02 then a divan is mandatory and isto be represented/positioned into zone configuration 02.

As a second example, the rule format 1606 is structured in a three foldslogic structure, namely “IF:-- THEN:-- WITH: --”. As an example, butwithout being limitative, the rule format may define the structure of arule example modeling a rule according to which IF: “ZONE CONFIGURATION= 02”, THEN: “DIVAN”, WITH: “LARGE RIGHT ARMREST”. This example maytranslate as if zone configuration=02 then a divan with a large rightarmrest is to be represented/positioned into zone configuration 02.

Seat Configuration

Turning now to FIGS. 17 and 18, embodiments of a method of propagating aconfiguration setting of a 3D model to other 3D models is illustrated.The method may be implemented by the seat configuration engine 274 ofthe configuration platform 260. In accordance with embodiments of thepresent technology, the method may allow configuring a particular 3Dmodel in accordance with a given configuration and then propagate thegiven configuration to other 3D models without a need to (re)configureeach one of the other 3D models manually. As an example, a 3D model maybe a first seat and a given configuration may comprise one or more of ashape, a layout, a selection of material type (e.g., certain patterns ona backrest, other patterns on the leg rest, a particular layout and/orcolor of pow lines, a particular wood selection for the armrest, aparticular selection of leathers, etc). A first seat may be an aircraftcabin seat. In this example, other 3D models may be a second seat, athird seat, etc. As a result of the execution of the method ofpropagating a configuration setting of a 3D model to other 3D models, auser may configure the first seat by selecting the requiredconfiguration and may propagate the required configuration to the secondseat, the third seat, etc without having to manually configure each oneof the second seat and the third seat.

In this example, a 3D model category is an aircraft cabin seat categorybut it should be envisioned that other types of 3D objects may be usedin conjunction with the method of propagating a configuration setting ofa 3D model to other 3D models without departing from the scope of thepresent technology (e.g., the 3D objects may be associated credenzas,side ledges, divans, etc).

In the example of FIG. 17, the 3D model is a first aircraft cabin seat1702 and another 3D model is a second aircraft cabin 1704. As it may beappreciated by a person skilled in the art of the present technology,FIG. 17 represents a front view of the first aircraft cabin seat 1702and a front view of the second aircraft cabin seat 1704. The firstaircraft cabin seat 1702 has a first layout while the aircraft cabinseat 1704 has a second layout, distinct from the first layout. In someembodiments, the first layout may be defined by a first pow line pattern(e.g., defining four surfaces for the back rest) while the second layoutmay be defined by a second pow line pattern (e.g., defining threesurfaces for the back rest).

In accordance with some embodiments of the present technology, the firstaircraft cabin seat 1702 is divided into a plurality of surfaces. Thefirst aircraft cabin seat 1702 may define a 3D model. The plurality ofsurfaces are 3D model surfaces that are visible to the user upon beingrendered by the 3D engine 272. In the embodiment of FIG. 17, theplurality of surfaces comprises four surfaces defining a back rest, onesurface defining a cushion, two surfaces defining a leg rest and twosurfaces defining a left armrest and a right armrest. In accordance withthe method, each one of the plurality of surfaces is associated with aunique surface identifier. In the example of FIG. 17, a first uniquesurface identifier “1” is associated with one of the surfaces of theback rest, a second unique surface identifier “2” is associated with oneof the surfaces of the back rest, a third unique surface identifier “3”is associated with one of the surfaces of the back rest, a fourth uniquesurface identifier “4” is associated with one of the surfaces of theback rest, a fifth unique surface identifier “5” is associated with thesurface of the cushion, a sixth unique surface identifier “6” isassociated with the right armrest, a seventh unique surface identifier“7” is associated with the left armrest, an eight unique surfaceidentifier “8” is associated with one of the surfaces of the leg restand a ninth unique surface identifier “9” is associated with one of thesurfaces of the leg rest.

The second aircraft cabin seat 1704 may define another 3D model beingpart of a same 3D model category than the first aircraft cabin seat 1702(i.e., aircraft cabin seat category). As for the first aircraft cabinseat 1702, the second aircraft cabin seat 1704 may be divided into aplurality of surfaces. The plurality of surfaces are 3D model surfacesthat are visible to the user upon being rendered by the 3D engine 272.In the embodiment of FIG. 17, the plurality of surfaces comprises threesurfaces defining a back rest, one surface defining a cushion, onesurface defining a leg rest and two surfaces defining a left armrest anda right armrest. In accordance with the method, a correspondence isestablished between the plurality of surfaces of the first aircraftcabin seat 1704 and another plurality of surfaces of the second aircraftcabin seat 1706. The correspondence may be established based oncorrespondences between the 3D model associated with the first aircraftcabin seat 1704 and another 3D model associated with the second aircraftcabin seat 1706. In some embodiments, the correspondence may be based ondata generated and/or stored by the CMS 220 (e.g., the Super BOM Library227, the Super BOM Meta Data 228, the Material Library 224). Once thecorrespondence is established, the method associates, for each one ofthe plurality of surfaces of the second aircraft cabin seat 1706, theunique surface identifier associated with the corresponding one of theplurality of surfaces of the first aircraft cabin seat 1704. In theillustrated example, the method associates the first unique surfaceidentifier “1” with one of the surfaces of the back rest, the secondunique surface identifier “2” with one of the surfaces of the back rest,the third unique surface identifier “3” with one of the surfaces of theback rest, the fifth unique surface identifier “5” with the surface ofthe cushion, the sixth unique surface identifier “6” with the rightarmrest, the seventh unique surface identifier “7” with the left armrestand the eight unique surface identifier “8” with the surface of the legrest. In the illustrated embodiment, determination has been made thatthe second aircraft cabin seat 1704 did not have surfaces correspondingto the unique surface identifier “4” and “9” of the first aircraft cabinseat 1702.

Once the correspondence between the plurality of surfaces of the firstaircraft cabin seat 1704 and another plurality of surfaces of the secondaircraft cabin seat 1706 is established, the method may determine aconfiguration setting to be applied to one or more of the plurality ofsurfaces of the first aircraft cabin seat 1704 and then propagate theconfiguration setting to the second aircraft cabin seat 1704.

In accordance with the above-described method, a user may select a woodmaterial to be applied on the surfaces of the left armrest and of theright armrest of the first aircraft cabin seat 1702 and the method mayautomatically apply the wood material to the surfaces of the leftarmrest and of the right armrest of the second aircraft cabin seat 1704.As another example, a user may select a leather material to be appliedon the surfaces of a portion of the back rest of the first aircraftcabin seat 1702 and the method may automatically apply the leathermaterial to the corresponding surfaces of the back rest of the secondaircraft cabin seat 1704.

Another example of how a 3D model is divided into a plurality ofsurfaces and how correspondence are established with a plurality ofsurfaces of another 3D model is provided at FIG. 18. FIG. 18 illustratesa first aircraft cabin seat back rest 1802 and a second aircraft cabinseat back rest 1804 in which correspondences have been established.

Having described, with reference to FIG. 1 to FIG. 18, some non-limitingexample instances of systems and computer-implemented methods used inconnection with operating a configuration platform, we shall nowdescribe a general approach with references to FIG. 19 to FIG. 23.

More specifically, FIG. 19 shows a flowchart illustrating a firstcomputer-implemented method 1900 implementing embodiments of the presenttechnology. The computer-implemented method of FIG. 19 may comprise acomputer-implemented method of converting a first set of data associatedwith a computer-aided design (CAD) system polygon meshes andconfiguration data, the method being executable by a processor of theone or more servers 240, 242 and 244, the method comprising a series ofsteps to be carried out by the one or more servers 240, 242 and 244.

The computer-implemented method of FIG. 19 may be carried out, forexample, in the context of the one or more servers 240, 242 and 244 bythe processor 110 executing program instructions having been loaded intorandom access memories 130 from solid-state drives 120 of the one ormore servers 240, 242 and 244 to implement the conversion pipeline 221.

The method 1900 starts at a step 1902 by accessing the first set ofdata, the first set of data defining a data collector associated with amonument of an aircraft cabin interior, the data collector comprising abody defining a 3D object representative of at least a portion of themonument and metadata defining information associated with the 3Dobject. Then, at a step 1904, the method proceeds to converting the bodyinto polygon meshes suitable for rendering by a 3D real-time engine of aconfiguration platform.

Then, at a step 1906, the method proceeds to generating, based on ananalysis of the metadata, configuration data, the configuration datacomprising at least one of a positioning of the monument, a materialsurface associated with the monument, a material grain directionassociated with the monument, lighting associated with the monument,annotations associated with the monument, alternate states associatedwith the monument and a kinematic sequence associated with the monument.

At a step 1908, the method proceeds to compiling the polygon meshes andthe configuration data in a data format suitable for representation andbehaviours by the 3D real-time engine.

In some embodiments, the data collector comprises one of a basiccollector and a standard part collector, the basic collector beingassociated with a representation of a structure of the portion of themonument and the standard part collector being associated with arepresentation of accessories associated with the portion of themonument.

In some embodiments, the metadata defines at least one of aconfigurability of the monument and a relationship of the data collectorwith other data collectors defining other portions of the monument. Insome embodiments, the data collector defines at least one of an envelopecollector, a zone configuration collector and a design featurecollector. In some embodiments, the envelope collector, the zoneconfiguration collector and the design feature collector definesavailable configuration permutations of the monument.

In some embodiments, the zone configuration collector depends fromanother zone configuration collector. In some embodiments, the designfeature collector depends from another design feature collector. In someembodiments, the zone configuration collector depending from anotherzone configuration collector and the design feature collector dependingfrom another design feature collector comprises one of a singlecross-dependency and a multiple cross-dependency. In some embodiments,converting the body into the polygon meshes further comprises convertingprojection mapping of a material associated with the body. In someembodiments, the method 1900 further comprises calculating a UV mappingon the polygon mesh. In some embodiments, the body is further associatedwith parameters defining a property of the material, the parametersbeing reflective of at least one of a finish type associated with thematerial, a scale associated with the material, a position associatedwith the material, a position associated with the material and aposition associated with the material.

In some embodiments, the monument is associated with a positionidentifier allowing positioning of the monument within the aircraftcabin interior. In some embodiments, the method 1900 further comprisesfurther to accessing the first set of data, proceeds to parsing thefirst set of data.

More specifically, FIG. 20 shows a flowchart illustrating a secondcomputer-implemented method 2000 implementing embodiments of the presenttechnology. The computer-implemented method of FIG. 20 may comprise acomputer-implemented method of operating a configuration platform, themethod being executable by a processor of the one or more servers 240,242 and 244, the method comprising a series of steps to be carried outby the one or more servers 240, 242 and 244.

The computer-implemented method of FIG. 20 may be carried out, forexample, in the context of the one or more servers 240, 242 and 244 bythe processor 110 executing program instructions having been loaded intorandom access memories 130 from solid-state drives 120 of the one ormore servers 240, 242 and 244 to implement the client side application270.

The method 2000 starts at a step 2002 by accessing, from a contentmanagement system, monument data representative of at least a portion ofa monument of an aircraft cabin interior, the monument data comprisingpolygon meshes suitable for rendering of the portion of the monument bya 3D real-time engine and configuration data, the configuration datacomprising at least one of a positioning of the monument, a materialsurface associated with the monument, a material grain directionassociated with the monument, lighting associated with the monument,annotations associated with the monument, alternate states associatedwith the monument and a kinematic sequence associated with the monument.

Then, at a step 2004, the method proceeds to determining, based on theconfiguration data, at least one of the positioning of the monument, thematerial surface associated with the monument, the material graindirection associated with the monument, the lighting associated with themonument, the annotations associated with the monument, the alternatestates associated with the monument and the kinematic sequenceassociated with the monument.

Then, at a step 2006, the method proceeds to rendering the portion ofthe monument by the 3D real-time engine.

In some embodiments, the configuration data is associated with one of abasic collector and a standard part collector, the basic collector beingassociated with a representation of a structure of the portion of themonument and the standard part collector being associated with arepresentation of accessories associated with the portion of themonument.

In some embodiments, the one of the basic collector and the standardpart collector defines a configurability of the monument and arelationship of the one of the basic collector and the standard partcollector with other collectors defining the monument.

In some embodiments, the one of the basic collector and the standardpart collector defines at least one of an envelope collector, a zoneconfiguration collector and a design feature collector.

In some embodiments, the envelope collector, the zone configurationcollector and the design feature collector defines availableconfiguration permutations of the monument.

In some embodiments, the body is further associated with parametersdefining a property of the material, the parameters being reflective ofat least one of a finish type associated with the material, a scaleassociated with the material, a position associated with the material, aposition associated with the material and a position associated with thematerial.

In some embodiments, the monument is associated with a positionidentifier allowing positioning of the monument within the aircraftcabin interior.

In some embodiments, the rendering is based on at least one of the oneof the basic collector and the standard part collector, the parametersdefining the property of the material and the position identifier.

More specifically, FIG. 21 shows a flowchart illustrating a thirdcomputer-implemented method 2100 implementing embodiments of the presenttechnology. The computer-implemented method of FIG. 21 may comprise acomputer-implemented method of of updating a content management systemassociated with a configuration platform, the method being executable bya processor of the one or more servers 240, 242 and 244, the methodcomprising a series of steps to be carried out by the one or moreservers 240, 242 and 244.

The computer-implemented method of FIG. 21 may be carried out, forexample, in the context of the one or more servers 240, 242 and 244 bythe processor 110 executing program instructions having been loaded intorandom access memories 130 from solid-state drives 120 of the one ormore servers 240, 242 and 244 to implement the material bridge 223.

The method 2100 starts at a step 2102 by accessing the contentmanagement system, the content management system comprising monumentdata representative of a monument of an aircraft cabin interior, themonument data comprising polygon meshes suitable for rendering of atleast a portion of the monument by a 3D real-time engine andconfiguration data, the configuration data comprising at least one of apositioning of the monument, a material surface associated with themonument, a material grain direction associated with the monument,lighting associated with the monument, annotations associated with themonument, alternate states associated with the monument and a kinematicsequence associated with the monument.

Then, at a step 2104, the method proceeds to accessing parametersdefining a property of a material, the parameters being reflective of atleast one of a finish type associated with the material, a scaleassociated with the material, a position associated with the materialand a position associated with the material.

Then, at a step 2106, the method proceeds to defining applicability ofthe parameters to the monument. Then, at a step 2108, the methodproceeds to assigning, based on the defined applicability of theparameters to the monument, a component identifier to the monument dataand to other monuments data based on a relationship between the monumentdata and the other monuments data.

In some embodiments, the method 2100 further comprises modifying theapplicability of the parameters to the monument and propagating theapplicability to the monument data and to the other monuments data.

More specifically, FIG. 22 shows a flowchart illustrating a fourthcomputer-implemented method 2200 implementing embodiments of the presenttechnology. The computer-implemented method of FIG. 22 may comprise acomputer-implemented method of of applying configuration rules, theconfiguration rules relating to an operation of a configurationplatform, the method being executable by a processor of the one or moreservers 240, 242 and 244, the method comprising a series of steps to becarried out by the one or more servers 240, 242 and 244.

The computer-implemented method of FIG. 22 may be carried out, forexample, in the context of the one or more servers 240, 242 and 244 bythe processor 110 executing program instructions having been loaded intorandom access memories 130 from solid-state drives 120 of the one ormore servers 240, 242 and 244 to implement the rule engine 275.

The method 2200 starts at a step 2202 by accessing, from a contentmanagement system, monument data representative of a monument of anaircraft cabin interior, the monument data comprising polygon meshessuitable for rendering of a portion of the monument by a 3D real-timeengine and configuration data, the configuration data comprising atleast one of a positioning of the monument, a material surfaceassociated with the monument, a material grain direction associated withthe monument, lighting associated with the monument, annotationsassociated with the monument, alternate states associated with themonument and a kinematic sequence associated with the monument.

Then, at a step 2204, the method proceeds to accessing configurationrules data, the configuration rules data modeling internal monumentconfiguration rules and external monument configuration rules, theinternal monument configuration rules relating to an internalconfiguration of the monument affecting the monument itself and theexternal monument configuration rules relating to an externalconfiguration of the monument affecting an environment in which themonument is to be represented.

Then, at a step 2206, the method proceeds to applying at least a subsetof the configuration rules data to the monument data.

Then, at a step 2208, the method proceeds to rendering the monument bythe 3D real-time engine, the rendering being based on the internalconfiguration rules and the external configuration rules to representthe portion of the monument.

In some embodiments, the method 2200 further comprises editing theconfiguration rules data by at least one adding internal monumentconfiguration rules or external monument configuration rules, removinginternal monument configuration rules or external monument configurationrules and modifying internal monument configuration rules or externalmonument configuration rules.

In some embodiments, the configuration rules model at least one ofcertification constraints, a position of a bulkhead within the aircraftcabin interior, available configurations of the monument for a givenposition of the monument within the aircraft cabin interior.

In some embodiments, the rendering further comprises positioning themonument within the aircraft cabin interior based on the configurationrules.

In some embodiments, the rendering further comprises selecting arepresentation of the monument based on the configuration rules.

In some embodiments, the configuration rules comprise a status to beassociated to the monument upon meeting configuration conditions, thestatus consisting of one of inherent, mandatory, unavailable, availableand replace with.

In some embodiments, the configuration conditions are based on at leastone of an option associated with the monument, the monument, an envelopeof the monument, a zone configuration associated with the monument and adesign feature configuration associated with the monument.

In some embodiments, the configuration data is associated with one of abasic collector and a standard part collector, the basic collector beingassociated with a representation of a structure of the monument and thestandard part collector being associated with a representation ofaccessories associated with the portion of the monument.

In some embodiments, the one of the basic collector and the standardpart collector defines a configurability of the monument and arelationship of the one of the basic collector and the standard partcollector with other collectors defining the monument.

In some embodiments, the one of the basic collector and the standardpart collector defines at least one of an envelope collector, a zoneconfiguration collector and a design feature collector.

In some embodiments, the configuration conditions are based on at leastone of the envelope collector, the zone configuration collector and thedesign feature collector.

More specifically, FIG. 23 shows a flowchart illustrating a fifthcomputer-implemented method 2300 implementing embodiments of the presenttechnology. The computer-implemented method of FIG. 23 may comprise acomputer-implemented method of propagating a configuration setting of a3D model to other 3D models, the 3D model and the other 3Ds being partof a same 3D model category, the method being executable by a processorof the one or more servers 240, 242 and 244, the method comprising aseries of steps to be carried out by the one or more servers 240, 242and 244.

The computer-implemented method of FIG. 23 may be carried out, forexample, in the context of the one or more servers 240, 242 and 244 bythe processor 110 executing program instructions having been loaded intorandom access memories 130 from solid-state drives 120 of the one ormore servers 240, 242 and 244 to implement the seat configuration engine274.

The method 2300 starts at a step 2302 by dividing the 3D model into afirst plurality of surfaces, the first plurality of surfaces being 3Dmodel surfaces visible upon being rendered by a 3D engine.

Then, at a step 2304, the method proceeds to associating to each one ofthe first plurality of surfaces, a unique surface identifier.

Then, for each one of the other 3D models, the method proceeds to steps2306-2310. The step 2306 comprises dividing the one of the other 3Dmodels into a second plurality of surfaces. The step 2308 comprisesestablishing a correspondence between at least some of the secondplurality of surfaces and at least some of the first plurality ofsurfaces, based on a correspondence between the 3D model and the one ofthe other 3D models. The step 2310 comprises associating, for each oneof the second plurality of surfaces corresponding to one of the firstplurality of surfaces, the unique surface identifier associated with thecorresponding one of the first plurality of surfaces.

At a step 2312, the method proceeds to selecting the configurationsetting of the 3D model. Then, at a step 2314, the method proceeds todetermining the unique identifier of the 3D model to which theconfiguration setting is to be applied. Then, at a step 2316, the methodproceeds to propagating, based on the unique identifier of the 3D model,the configuration setting to the other 3D models to which theconfiguration setting is to be applied.

In some embodiments, the 3D model is an aircraft cabin seat. In someembodiments, the first plurality of surfaces comprises a plurality ofthe surfaces of the aircraft cabin seat. In some embodiments, selectingthe configuration setting comprises selecting a material type of theaircraft cabin seat. In some embodiments, propagating the configurationsetting comprises propagating a selection of the material type of anaircraft cabin seat to other aircraft cabin seats.

While the above-described implementations have been described and shownwith reference to particular steps performed in a particular order, itwill be understood that these steps may be combined, sub-divided, orre-ordered without departing from the teachings of the presenttechnology. Accordingly, the order and grouping of the steps is not alimitation of the present technology.

It should be expressly understood that not all technical effectsmentioned herein need to be enjoyed in each and every embodiment of thepresent technology. For example, embodiments of the present technologymay be implemented without the user enjoying some of these technicaleffects, while other embodiments may be implemented with the userenjoying other technical effects or none at all.

Modifications and improvements to the above-described implementations ofthe present technology may become apparent to those skilled in the art.The foregoing description is intended to be exemplary rather thanlimiting. The scope of the present technology is therefore intended tobe limited solely by the scope of the appended claims.

1. A method of converting a first set of data associated with acomputer-aided design (CAD) system polygon meshes and configurationdata, the method comprising: accessing the first set of data, the firstset of data defining a data collector associated with a monument of anaircraft cabin interior, the data collector comprising a body defining a3D object representative of at least a portion of the monument andmetadata defining information associated with the 3D object; convertingthe body into polygon meshes suitable for rendering by a 3D real-timeengine of a configuration platform; generating, based on an analysis ofthe metadata, configuration data, the configuration data comprising atleast one of a positioning of the monument, a material surfaceassociated with the monument, a material grain direction associated withthe monument, lighting associated with the monument, annotationsassociated with the monument, alternate states associated with themonument and a kinematic sequence associated with the monument; andcompiling the polygon meshes and the configuration data in a data formatsuitable for representation and behaviours by the 3D real-time engine.2. The method of claim 1, wherein the data collector comprises one of abasic collector and a standard part collector, the basic collector beingassociated with a representation of a structure of the portion of themonument and the standard part collector being associated with arepresentation of accessories associated with the portion of themonument.
 3. The method of claim 2, wherein the metadata defines atleast one of a configurability of the monument and a relationship of thedata collector with other data collectors defining other portions of themonument.
 4. The method of claim 3, wherein the data collector definesat least one of an envelope collector, a zone configuration collectorand a design feature collector.
 5. The method of claim 4, wherein theenvelope collector, the zone configuration collector and the designfeature collector defines available configuration permutations of themonument.
 6. The method of claim 5, wherein the zone configurationcollector depends from another zone configuration collector.
 7. Themethod of claim 6, wherein the design feature collector depends fromanother design feature collector.
 8. The method of claim 7, wherein thezone configuration collector depending from another zone configurationcollector and the design feature collector depending from another designfeature collector comprises one of a single cross-dependency and amultiple cross-dependency.
 9. The method of claim 1, wherein convertingthe body into the polygon meshes further comprises converting projectionmapping of a material associated with the body.
 10. The method of claim9, further comprising calculating a UV mapping on the polygon mesh. 11.The method of claim 10, wherein the body is further associated withparameters defining a property of the material, the parameters beingreflective of at least one of a finish type associated with thematerial, a scale associated with the material, a position associatedwith the material, a position associated with the material and aposition associated with the material.
 12. The method of claim 11,wherein the monument is associated with a position identifier allowingpositioning of the monument within the aircraft cabin interior.
 13. Themethod of claim 1, wherein further to accessing the first set of data,the method proceeds to parsing the first set of data. 14.-34. (canceled)35. A computer-implemented system for converting a first set of dataassociated with a computer-aided design (CAD) system polygon meshes andconfiguration data, the system comprising: a processor; a non-transitorycomputer-readable medium coupled to the processor and storinginstructions executable by the processor and configured to cause theprocessor to perform: accessing the first set of data, the first set ofdata defining a data collector associated with a monument of an aircraftcabin interior, the data collector comprising a body defining a 3Dobject representative of at least a portion of the monument and metadatadefining information associated with the 3D object; converting the bodyinto polygon meshes suitable for rendering by a 3D real-time engine of aconfiguration platform; generating, based on an analysis of themetadata, configuration data, the configuration data comprising at leastone of a positioning of the monument, a material surface associated withthe monument, a material grain direction associated with the monument,lighting associated with the monument, annotations associated with themonument, alternate states associated with the monument and a kinematicsequence associated with the monument; and compiling the polygon meshesand the configuration data in a data format suitable for representationand behaviours by the 3D real-time engine. 36.-38. (canceled)
 39. Acomputer-implemented system configured to perform the method of claim 1.40. A non-transitory computer-readable medium comprisingcomputer-executable instructions that cause a system to execute themethod according to claim
 1. 41.-46. (canceled)
 47. A system foroperating a configuration platform, the system comprising: a conversionpipeline, the conversion pipeline allowing converting a first set ofdata associated with a computer-aided design (CAD) system into polygonmeshes suitable for rendering of the portion of a monument andconfiguration data, the configuration data comprising at least one of apositioning of the monument, a material surface associated with themonument, a material grain direction associated with the monument,lighting associated with the monument, annotations associated with themonument, alternate states associated with the monument and a kinematicsequence associated with the monument; a content management system, thecontent management system storing the polygon meshes and theconfiguration data; and a 3D real-time engine, the 3D real-time engineallowing to determine, based on the configuration data, at least one ofthe positioning of the monument, the material surface associated withthe monument, the material grain direction associated with the monument,the lighting associated with the monument, the annotations associatedwith the monument, the alternate states associated with the monument andthe kinematic sequence associated with the monument; and to render theportion of the monument by the 3D real-time engine.
 48. The system ofclaim 47, wherein the system further comprises a material bridge, thematerial bridge being configured to: access parameters defining aproperty of a material, the parameters being reflective of at least oneof a finish type associated with the material, a scale associated withthe material, a position associated with the material, a positionassociated with the material and a position associated with thematerial; define applicability of the parameters to the monument; andassign, based on the defined applicability of the parameters to themonument, a component identifier to the monument data and to othermonuments data based on a relationship between the monument data and theother monuments data.
 49. The system of claim 47, wherein the systemfurther comprises a rule engine, the rule engine being configured to:access configuration rules data, the configuration rules data modelinginternal monument configuration rules and external monumentconfiguration rules, the internal monument configuration rules relatingto an internal configuration of the monument affecting the monument andthe external monument configuration rules relating to an externalconfiguration of the monument affecting an environment in which themonument is to be represented; apply at least a subset of theconfiguration rules data to the monument data; and render the monumentby the 3D real-time engine, the rendering being based on the internalconfiguration rules and the external configuration rules to representthe portion of the monument.
 50. The system of claim 47, wherein thesystem further comprises a configuration engine, the configurationengine being configured to propagate a configuration setting of a 3Dmodel to other 3D models, the 3D model and the other 3Ds being part of asame 3D model category.